Method for implimenting request from app by sim in mobile phone

ABSTRACT

A method for implementing requests from an app by a SIM in a mobile phone comprises the steps of: binding an app to a BIP server by a mobile phone; delivering a request command to the BIP server from the mobile phone; converting the request command to an APDU format, packing the converted request command in the APDU format in a request packet, and delivering the request packet to an IP of a SIM by the BIP server; receiving and unpacking the request packet to have the converted request command, and providing the converted request command to the SIM; executing the request command to have a result by the SIM; delivering the result in a response packet to the BIP server via the mobile network relayed; unpacking the response packet to fetch the result, and delivering the result to the mobile phone for the app by the BIP server.

FIELD OF THE INVENTION

The present invention relates to a method for implementing request froman app. More particularly, the present invention relates to a method forimplementing request from an app by a SIM in a mobile phone.

BACKGROUND OF THE INVENTION

In a communication device, such as a mobile phone, communication andcooperation between software and hardware may not be allowed. Ifpossible, it may need to come through the system operator. An obviousexample is the interaction between APP and Subscriber Identity Module(SIM) in the mobile phone. Any data and application in the SIM can beaccessed and updated in two ways: one is that the mobile operator issuesinstructions to the SIM card through OTA server for the APP, and theother is that the APP communications with the SIM card through the menuon the SIM tool kit (STK) to activate certain functions from time totime. Realization of the functions is mostly done by the modem side,which involves short message service protocol or bearer independentprotocol (BIP) protocol. However, not all mobile operators provideservice for APP developer to access the SIM through their hardwarearchitecture. Meanwhile, not all operating systems of the mobile phonespermit APP to utilize BIP to access the SIM.

Today, the SIM (card) is not only used to store user identificationdata, text message data and phone numbers. Because the SIM is not easilyaccessible and has the convenience to carry and transfer, the SIM hasbeen used to store confidential and high-value information. For example,the SIM may store public and private keys of cryptocurrency as a coldwallet. For a smooth channel to fetch or updated the stored information,a control APP has to access the SIM without any obstacle therebetween.As mentioned above, this is so far not available.

SUMMARY OF THE INVENTION

This paragraph extracts and compiles some features of the presentinvention; other features will be disclosed in the follow-up paragraphs.It is intended to cover various modifications and similar arrangementsincluded within the spirit and scope of the appended claims.

A method for implementing requests from an app by a SIM in a mobilephone is disclosed. It comprises the steps of: a) binding an app to abearer independent protocol (BIP) server by a mobile phone where the appis installed; b) delivering a request command to the BIP server from themobile phone by the app; c) converting the format of the request commandto an Application Protocol Data Unit (APDU) format, packing theconverted request command in the APDU format in a request packet, anddelivering the request packet to an IP of a SIM by the BIP server via amobile network; d) receiving and unpacking the request packet to havethe converted request command, and providing the converted requestcommand to the SIM by the mobile phone; e) executing the request commandto have a result by the SIM; f) delivering the result in a responsepacket to the BIP server via the mobile network relayed by the mobilephone by the SIM; g) unpacking the response packet to fetch the result,and delivering the result to the mobile phone for the app by the BIPserver. Data delivered between the SIM and the BIP server via the mobilephone is encrypted.

Another method for implementing requests from an app by a SIM in amobile phone is also disclosed. It comprises the steps of: a) binding anapp to a BIP server by a mobile phone where the app is installed; b)delivering an encrypting request command with an object to the BIPserver by the mobile phone; c) cutting the object into a plurality ofpieces, converting a plurality of amended encrypting request commands inan APDU format from the encrypting request command, and packing eachamended encrypting request command with a specific piece in a requestpacket, respectively, by the BIP server; d) delivering one requestpacket to an IP of a SIM by the BIP server via a mobile network; e)receiving and unpacking the request packet to have the amendedencrypting request command and corresponding piece, and providing theamended encrypting request command with the piece to the SIM by themobile phone; f) executing the amended encrypting request command toencrypt the piece according to an encryption algorithm to have aninitial result by the SIM; g) packing the initial result in a responsepacket and delivering the response packet to the mobile phone by theSIM; h) delivering the response packet to the BIP server via the mobilenetwork by the mobile phone; i) repeating the step d) to the step h) forthe other request packet; and j) unpacking the response packets to fetchthe initial results, combining the encrypted pieces as an encryptedobject in a final result, and delivering the final result to the mobilephone for the app by the BIP server. Data delivered between the SIM andthe BIP server via the mobile phone is encrypted.

Still another method for implementing requests from an app by a SIM in amobile phone is disclosed. It comprises the steps of: a) binding an appto a BIP server by a mobile phone where the app is installed; b)delivering a decrypting request command with an encrypted object to bedecrypted to the BIP server by the mobile phone; c) cutting the objectinto a plurality of pieces, converting a plurality of amended decryptingrequest commands in an APDU format from the decrypting request command,and packing each amended decrypting request command with a specificpiece in a request packet, respectively, by the BIP server; d)delivering one request packet to an IP of a SIM by the BIP server via amobile network; e) receiving and unpacking the request packet to havethe amended decrypting request command and corresponding piece, andproviding the amended decrypting request command with the piece to theSIM by the mobile phone; f) executing the amended decrypting requestcommand to decrypt the piece according to an encryption algorithm tohave an initial result by the SIM; g) packing the initial result in aresponse packet and delivering the response packet to the mobile phoneby the SIM; h) delivering the response packet to the BIP server via themobile network by the mobile phone; i) repeating the step d) to the steph) for the other request packet; and j) unpacking the response packetsto fetch the initial results, combining the decrypted pieces as adecrypted object in a final result, and delivering the final result tothe mobile phone for the app by the BIP server. Data delivered betweenthe SIM and the BIP server via the mobile phone is encrypted.

Preferably, data between the BIP server and the mobile phone isconformed to Hyper Text Transfer Protocol (HTTP).

Preferably, the result unpacked from the response packet is furtherconverted to a format of JSON.

Preferably, the communication processes between the mobile phone and theBIP server are further encrypted according to Hyper Text TransferProtocol Secure (HTTPS) protocol.

Preferably, the request command is verifying an attached PersonalIdentification Number (PIN) and the SIM compares the PIN with a presetvalue.

Preferably, the request command is selecting a file and the SIM providesnames of all files stored therein as the result.

Preferably, the request command is reading a selected file and the SIMprovides the selected file stored therein as the result.

Preferably, the encryption algorithm is Advanced Encryption Standard(AES) or Rivest-Shamir-Adleman (RSA).

Preferably, a type of the SIM is a slim SIM, an eSIM, an integrated SIM(iSIM) or a SIM card.

Preferably, the step a) further comprises sub-steps of: a1) delivering atoken request with an inputted third party number for an app to a BIPserver by a mobile phone where the app is installed; a2) delivering atemporary permission token to the app via the mobile phone by the BIPserver; a3) delivering a binding request for the app to the BIP serverby the mobile phone; and a4) binding the third party number with aregistered number in the BIP server, providing a permanent token to theapp and delivering a successful binding message to the app via themobile phone by the BIP server.

Preferably, it further comprises steps of: a5) delivering a failedbinding message with a binding code to the app via the mobile phone bythe BIP server when the step a4) is failed; a6) delivering the bindingcode to the BIP server for rebinding by the mobile phone; and a7)binding the third party number with a registered number in the BIPserver again, providing another permanent token to the app anddelivering a successful binding message to the app via the mobile phoneby the BIP server.

With the BIP server, communication between the app and the SIM in themobile phone and becomes possible.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an implementation architecture for the method for implementrequest from an app in a mobile according to the present invention.

FIG. 2 is a flow chart of a first embodiment of a method according tothe present invention.

FIG. 3 is a flow chart of a second embodiment of another methodaccording to the present invention.

FIG. 4 illustrates how an object is changed by a BIP server.

FIG. 5 is a flow chart of a third embodiment of another method accordingto the present invention.

FIG. 6 illustrates how an encrypted object is changed by a BIP server.

FIG. 7 is a flow chart of a binding procedure according to the presentinvention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The present invention will now be described more specifically withreference to the following embodiments.

Before the method for implement request from an app in a mobile(hereinafter referred to as the method) is disclosed, an implementationarchitecture for the method is illustrated. Please refer to FIG. 1 .According to the present invention, a BIP server 20 is required. The BIPserver 20 acts as an intermediary and a translator, for communicatingbetween a SIM 11 in a mobile phone 10 and an app 40 operated by anoperating system 12 of the mobile device 10. A type of the SIM may be aslim SIM, an eSIM, an integrated SIM (iSIM) or a SIM card. The BIPserver 20 connects to the mobile phone 10 through a mobile network 1. Ifthe app 40 is further controlled by an app server 30, the app server 30is in the implementation architecture, too. The mobile phone 10 may beof other type, such as a tablet, a wear device, an internet of things(IOT) device, etc. In the embodiment, the mobile phone used is just forillustration. It should be emphasized that data between the BIP server20 and the mobile phone 10 may be conformed to Hyper Text TransferProtocol (HTTP) in the following embodiments, including request packetsand response packet. Meanwhile, data delivered between the SIM 11 andthe BIP server 20 via the mobile phone 10 may be encrypted. Thecommunication processes between the mobile phone 10 and the BIP servermay be further encrypted according to Hyper Text Transfer ProtocolSecure (HTTPS) protocol.

Please refer to FIG. 2 . It is a flow chart of a first embodiment of themethod according to the present invention. The first embodimentdiscloses only how the SIM 11 is accessed by the app 40. A first step ofthe first embodiment is binding the app 40 to the BIP server 20 by themobile phone 10 where the app 40 is installed (S01). Binding meansestablishing a “relation” between the app 40 and the BIP server 20,letting the BIP server 20 know the app 40 and accepts the app 40 forfollowing steps. For some security reasons, not all app s, such as amalware, are allowed to work through the BIP server 20. Therefore,binding (or registration) is a must. There are many binding ways in thefield of information technology and use of binding is not limited by thepresent invention. A recommendation will be provided later. Then, asecond step of the first embodiment is delivering a request command tothe BIP server 20 from the mobile phone 10 by the app 40 (S02). Therequest command is to ask the SIM 11 for something via the BIP server20. For example, the request command may be verifying an attachedPersonal Identification Number (PIN). Thus, the SIM 11 will compare thePIN with a preset value stored therein after receiving the requestcommand. The request command may also be selecting a file. The SIM 11will provide names of all files stored therein as a result (definitionof the result will be described in detail later) according to therequest command. The request command may further be reading a selectedfile. The SIM 11 will provide the selected file, e.g., a file comprisesa public key and a private key of cryptocurrency, stored therein as theresult. The format of the request commend is not restricted. Inpractice, the mobile device 10 may implement communication with the BIPserver 20 through BIP APIs.

Next, a third step of the first embodiment is converting the format ofthe request command to an (APDU) format, packing the converted requestcommand in the APDU format in a request packet, and delivering therequest packet to an IP of a SIM by the BIP server 20 via the mobilenetwork 1 (S03). In this step, there are three sub-steps. The firstsub-step is converting the format of the request command to the APDUformat. APDU is a part of the application layer in the Open SystemsInterconnection Reference model that is used for communication betweentwo separate device's applications. In the context of smart cards, anAPDU is the communication unit between a smart card reader and a smartcard. Namely, use of APDU format for the request command is to let theSIM 11 know what the request command is with its language. It should beemphasized that converting is done by the BIP server 20, rather than themobile phone 10 as the conventional way to do. The second sub-step is topack the converted request command a request packet. Packing can beimplemented by many methods, for example, adding header and footer toit. The third sub-step is to deliver the request packet. One of theimportant spirits of the present invention is that the delivery goesthrough a mobile network. It is not workable for telecommunicationsnetwork. The purpose of this sub-step is to link the BIP server 20 withthe SIM 11 and then process data delivery. If the mobile phone 10 goesthrough a telecommunications network, it might be behind a floating IPof an IP sharer. The BIP server 20 cannot find the SIM 11 with its IP.

The fourth step is receiving and unpacking the request packet to havethe converted request command, and providing the converted requestcommand to the SIM 11 by the mobile phone 10 (S04). When the requestpacket is unpacked, e.g., removing the header and the footer, theconverted request command in APDU format is available. Then, the fifthstep begins by executing the request command to have the result by theSIM 11 (S05). The result is defined as what responds to the requestcommand. For example, if the request command is selecting a file, theresult is a list of the names of all files. Definitions and examples ofthe request command and the result are applicable to other embodiments.

Next, the sixth step is delivering the result in a response packet tothe BIP server 20 via the mobile network 1 relayed by the mobile phone10 by the SIM 11 (S06). The response packet, like the request packet, ispacked by a header and a footer for delivery. The format of the responsepacket is also APDU. The last step of the first embodiment is unpackingthe response packet to fetch the result, and delivering the result tothe mobile phone 10 for the app 40 by the BIP server 20 (S07). Theresult may be shown on the mobile phone 10 or sent to the app server 30for further use. Preferably, result unpacked from the response packetcan be further converted to a format of JSON which is readable by manyapps.

In the first embodiment, the method provides a way to access the SIM 11for the app 40. In a second embodiment, a method for implement requestfrom an app in a mobile (hereinafter referred to as this method todistinguish from the method used in the first embodiment) according tothe present invention can further ask the SIM 11 to encrypt an object,e.g., a file or a message in any format with an encryptor built in theSIM 11 is disclosed. In the description for the second embodiment, theimplementation architecture in FIG. 1 is also applicable.

Please refer to FIG. 3 . It is a flow chart of the second embodiment ofthis method according to the present invention. The first step of thesecond embodiment is binding an app to the BIP server 20 by the mobilephone 10 where the app 40 is installed (S11). It is the same as thefirst step of the first embodiment so that the details are not mentionedagain here. The second step of the second embodiment is delivering anencrypting request command with an object to the BIP server 20 by themobile phone 10 (S12). This step is different from the second step ofthe first embodiment. The request command sent is specified to ask foran encryption on the object. Meanwhile, the step is carried out by themobile phone 10, not necessary to be initiated by the app 40 accordingto the present invention.

Next, the third step of the second embodiment is cutting the object intoa plurality of pieces, converting a plurality of amended encryptingrequest commands in an APDU format from the encrypting request command,and packing each amended encrypting request command with a specificpiece in a request packet, respectively, by the BIP server 20 (S13). Inorder to have a better understanding on this step, please refer to FIG.4. It illustrates how the object is changed by the BIP server 20. InFIG. 4 , an object A is cut into two pieces, piece A and piece B. Thecutting method may be cutting object into two separate files. It mayalso be cutting the object by bits. Piece A doesn't have to have thesame size (bits) as piece B. The encrypting request command may be ascript or a command for an API used by the SIM 11. The BIP server 20will assign one amended encrypting request command in the APDU formatfor each piece. In FIG. 4 , an amended encrypting request command A isattached to piece A and the amended encrypting request command A andpiece A are packed in a request packet A. An amended encrypting requestcommand B is attached to piece B and the amended encrypting requestcommand B and piece B are packed in a request packet B. The amendedencrypting request command A and the amended encrypting request commandB will not only inform the SIM 11 to encrypt the attached piece but alsohave a message of connection that piece A and piece B are a part of theobject A. Packing method is the same as what is disclosed in the firstembodiment. It is not repeated again. The amended encrypting requestcommands are in APDU format so that the SIM 11 knows them.

The fourth step of the second embodiment is delivering one requestpacket to an IP of the SIM 11 by the BIP server 20 via the mobilenetwork 1 (S14). The purpose of the step S14 is to deliver a requestpacket at a time. The way why the delivery goes through mobile networkis also the same as what is disclosed in the first embodiment.

Next, a fifth step of the second embodiment is receiving and unpackingthe request packet to have the amended encrypting request command andcorresponding piece, and providing the amended encrypting requestcommand with the piece to the SIM 11 by the mobile phone 10 (S15). Now,the request packet A is received and unpacked by the mobile phone 10 andthe amended encrypting request command A and the piece A are provided tothe SIM 11.

Then, the sixth step is executing the amended encrypting request commandto encrypt the piece according to an encryption algorithm to have aninitial result by the SIM 11 (S16). The amended encrypting requestcommand A is executed so that piece A is encrypted. According to thepresent invention, the encryption algorithm may be and not limited toAdvanced Encryption Standard (AES) and Rivest-Shamir-Adleman (RSA). Theencrypted piece A is the initial result. The coming step of the secondembodiment is packing the initial result in a response packet anddelivering the response packet to the mobile phone 10 by the SIM 11(S17). The response packet comprising piece A with some otherdescription which may be in the form of header and footer is sent to themobile phone 10. The eighth step is delivering the response packet tothe BIP server 20 via the mobile network 1 by the mobile phone 10 (S18).Again, the response packet is further delivered to the BIP server 20.

Next, the ninth step of the second embodiment is repeating the step S14to the step S18 for the other request packet (S19). It means deliveringrequest packet B is delivered to the IP of the SIM 11 by the BIP server20 via the mobile network 1, the mobile phone 10 receives and unpacksthe request packet B to have the amended encrypting request command Band corresponding piece B, and provides the amended encrypting requestcommand B with the piece B to the SIM 11, the SIM 11 executes theamended encrypting request command B to encrypt piece B according to theencryption algorithm to have another initial result, the SIM 11 packsthe initial result in another response packet and delivers the responsepacket to the mobile phone 10, and the mobile phone 10 is furtherdelivers the response packet to the BIP server 20 via the mobile network1. The final step of the second embodiment is unpacking the responsepackets to fetch the initial results, combining the encrypted pieces asan encrypted object in a final result, and delivering the final resultto the mobile phone 10 for the app 40 by the BIP server 20 (S20). In theBIP server 20, both response packets are unpacked, and correspondinginitial results are obtained. The encrypted piece A and encrypted pieceB are fetched and combined to have the encrypted object. The encryptedobject is finally packed as the final result which is delivered to themobile phone 10 for the app 40 to use.

This method in the second embodiment asks the SIM 11 to encrypt theobject. On the other hand, according to the present invention, anencrypted object can also be decrypted by the SIM 11. In a thirdembodiment, a method for implement request from an app in a mobile(hereinafter referred to as said method to distinguish from the methodused in the first embodiment and the second embodiment) furtherdiscloses the whole processes. In the description for the thirdembodiment, the implementation architecture in FIG. 1 is alsoapplicable.

Please refer to FIG. 5 . It is a flow chart of the third embodiment ofthis method according to the present invention. The first step of thethird embodiment is binding an app to the BIP server 20 by the mobilephone 10 where the app 40 is installed (S21). It is the same as thefirst step of the first embodiment and the second embodiment so that thedetails are not mentioned again here. The second step of the secondembodiment is delivering a decrypting request command with an encryptedobject to the BIP server 20 by the mobile phone 10 (S22). This step isdifferent from the second step of the second embodiment. The requestcommand sent is specified to ask for a decryption on the encryptedobject.

Next, the third step of the third embodiment is cutting the object intoa plurality of pieces, converting a plurality of amended decryptingrequest commands in an APDU format from the decrypting request command,and packing each amended decrypting request command with a specificpiece in a request packet, respectively, by the BIP server 20 (S23). Inorder to have a better understanding on this step, please refer to FIG.6 . It illustrates how the encrypted object is changed by the BIP server20. In FIG. 6 , an object B is cut into two pieces, piece C and piece D.The cutting method is the same as what is disclosed in the secondembodiment. The BIP server 20 will assign one amended decrypting requestcommand in the APDU format for each piece. In FIG. 6 , an amendeddecrypting request command C is attached to piece C and the amendeddecrypting request command C and piece C are packed in a request packetC. An amended decrypting request command D is attached to piece D andthe amended decrypting request command D and piece D are packed in arequest packet D. The amended decrypting request command C and theamended decrypting request command D will not only inform the SIM 11 todecrypt the attached piece but also have a message of connection thatpiece C and piece D are a part of the object B. Packing method is thesame as what is disclosed in the first embodiment. It is not repeatedagain.

The fourth step of the third embodiment is delivering one request packetto an IP of the SIM 11 by the BIP server 20 via the mobile network 1(S24). The purpose of the step S24 is also to deliver a request packetat a time.

Next, a fifth step of the third embodiment is receiving and unpackingthe request packet to have the amended decrypting request command andcorresponding piece, and providing the amended decrypting requestcommand with the piece to the SIM 11 by the mobile phone 10 (S25). Now,the request packet C is received and unpacked by the mobile phone 10,and the amended decrypting request command C and the piece C areprovided to the SIM 11.

Then, the sixth step is executing the amended decrypting request commandto decrypt the piece according to an encryption algorithm to have aninitial result by the SIM 11 (S26). The amended decrypting requestcommand C is executed so that piece C is decrypted. Similarly, theencryption algorithm can be AES or RSA. The decrypted piece C is theinitial result. The coming step of the third embodiment is packing theinitial result in a response packet and delivering the response packetto the mobile phone 10 by the SIM 11 (S27). The response packetcomprising piece C with some other description which may be in the formof header and footer is sent to the mobile phone 10. The eighth step isdelivering the response packet to the BIP server 20 via the mobilenetwork 1 by the mobile phone 10 (S28). It is similar to step S18.

Next, the ninth step of the third embodiment is repeating the step S14to the step S18 for the other request packet (S29). It means deliveringrequest packet D is delivered to the IP of the SIM 11 by the BIP server20 via the mobile network 1, the mobile phone 10 receives and unpacksthe request packet D to have the amended decrypting request command Dand corresponding piece D, and provides the amended decrypting requestcommand D with the piece D to the SIM 11, the SIM 11 executes theamended decrypting request command D to decrypt piece D according to theencryption algorithm to have another initial result, the SIM 11 packsthe initial result in another response packet and delivers the responsepacket to the mobile phone 10, and the mobile phone 10 is furtherdelivers the response packet to the BIP server 20 via the mobile network1. The final step of the third embodiment is unpacking the responsepackets to fetch the initial results, combining the decrypted pieces asa decrypted object in a final result, and delivering the final result tothe mobile phone 10 for the app 40 by the BIP server 20 (S30). In theBIP server 20, both response packets are unpacked, and correspondinginitial results are obtained. The decrypted piece C and decrypted pieceD are fetched and combined to have the original object. The object isfinally packed as the final result which is delivered to the mobilephone 10 for the app 40 to use.

As mentioned earlier, the binding between the app 40 (through the mobilephone 10) and the BIP server 20 is also a portion of the presentinvention. Below describes how the binding is achieved.

Please see FIG. 7 . It is a flow chart of a binding procedure accordingto the present invention. It should be emphasized that all the steps ofthe binding procedure are applied before the first step in theembodiments above. The first step of the binding procedure is deliveringa token request with an inputted third party number for an app to a BIPserver by a mobile phone where the app is installed (Sa1). The tokenrequest is a certificate for the app 40 and used to ask a temporarypermission from the BIP server 20. The third party number is given bythe user of the app 40 for use in the registration in the future. Thesecond step of the binding procedure is delivering a temporarypermission token to the app 40 via the mobile phone 10 by the BIP server40 (Sa2). When the temporary permission token is sent, it means the app40 is accepted by the BIP server 40. However, the binding relationshipis not established now. The third step of the binding procedure isdelivering a binding request for the app 40 to the BIP server 20 by themobile phone 10 (Sa3). This step is formally to ask the BIP server tobuild the binding. Then, the fourth step of the binding procedure isbinding the third party number with a registered number in the BIPserver 20, providing a permanent token to the app 40 and delivering asuccessful binding message to the app40 via the mobile phone 10 by theBIP server 20 (Sa4). When binding is successful in the BIP server 20,the registered number will be generated and bound to the third partynumber by the BIP server 20. Meanwhile, the app 40 will receive thepermanent token for confirmation and the binding message to show to theuser.

However, if binding is not successful due to communication, the bindingprocedure has below processes. There are further three steps: deliveringa failed binding message with a binding code to the app 40 via themobile phone 10 by the BIP server 20 when the step a4) is failed;delivering the binding code to the BIP server 20 for rebinding by themobile phone 10; and binding the third party number with a registerednumber in the BIP server 20 again, providing another permanent token tothe app 40 and delivering a successful binding message to the app 40 viathe mobile phone 10 by the BIP server 20.

While the invention has been described in terms of what is presentlyconsidered to be the most practical and preferred embodiments, it is tobe understood that the invention needs not be limited to the disclosedembodiments. On the contrary, it is intended to cover variousmodifications and similar arrangements included within the spirit andscope of the appended claims, which are to be accorded with the broadestinterpretation so as to encompass all such modifications and similarstructures.

What is claimed is:
 1. A method for implementing requests from an app bya SIM in a mobile phone, comprising the steps of: a) binding an app to abearer independent protocol (BIP) server by a mobile phone where the appis installed; b) delivering a request command to the BIP server from themobile phone by the app; c) converting the format of the request commandto an Application Protocol Data Unit (APDU) format, packing theconverted request command in the APDU format in a request packet, anddelivering the request packet to an IP of a SIM by the BIP server via amobile network; d) receiving and unpacking the request packet to havethe converted request command, and providing the converted requestcommand to the SIM by the mobile phone; e) executing the request commandto have a result by the SIM; f) delivering the result in a responsepacket to the BIP server via the mobile network relayed by the mobilephone by the SIM; g) unpacking the response packet to fetch the result,and delivering the result to the mobile phone for the app by the BIPserver, wherein Data delivered between the SIM and the BIP server viathe mobile phone is encrypted.
 2. The method according to claim 1,wherein data between the BIP server and the mobile phone is conformed toHyper Text Transfer Protocol (HTTP).
 3. The method according to claim 1,wherein the result unpacked from the response packet is furtherconverted to a format of JSON.
 4. The method according to claim 1,wherein the communication processes between the mobile phone and the BIPserver are further encrypted according to Hyper Text Transfer ProtocolSecure (HTTPS) protocol.
 5. The method according to claim 1, wherein therequest command is verifying an attached Personal Identification Number(PIN) and the SIM compares the PIN with a preset value.
 6. The methodaccording to claim 1, wherein the request command is selecting a fileand the SIM provides names of all files stored therein as the result. 7.The method according to claim 1, wherein the request command is readinga selected file and the SIM provides the selected file stored therein asthe result.
 8. The method according to claim 1, wherein a type of theSIM is a slim SIM, an eSIM, an integrated SIM (iSIM) or a SIM card. 9.The method according to claim 1, the step a) further comprises sub-stepsof: a1) delivering a token request with an inputted third party numberfor an app to a BIP server by a mobile phone where the app is installed;a2) delivering a temporary permission token to the app via the mobilephone by the BIP server; a3) delivering a binding request for the app tothe BIP server by the mobile phone; and a4) binding the third partynumber with a registered number in the BIP server, providing a permanenttoken to the app and delivering a successful binding message to the appvia the mobile phone by the BIP server.
 10. The method according toclaim 9, further comprising steps of: a5) delivering a failed bindingmessage with a binding code to the app via the mobile phone by the BIPserver when the step a4) is failed; a6) delivering the binding code tothe BIP server for rebinding by the mobile phone; and a7) binding thethird party number with a registered number in the BIP server again,providing another permanent token to the app and delivering a successfulbinding message to the app via the mobile phone by the BIP server.
 11. Amethod for implementing requests from an app by a SIM in a mobile phone,comprising the steps of: a) binding an app to a BIP server by a mobilephone where the app is installed; b) delivering an encrypting requestcommand with an object to the BIP server by the mobile phone; c) cuttingthe object into a plurality of pieces, converting a plurality of amendedencrypting request commands in an APDU format from the encryptingrequest command, and packing each amended encrypting request commandwith a specific piece in a request packet, respectively, by the BIPserver; d) delivering one request packet to an IP of a SIM by the BIPserver via a mobile network; e) receiving and unpacking the requestpacket to have the amended encrypting request command and correspondingpiece, and providing the amended encrypting request command with thepiece to the SIM by the mobile phone; f) executing the amendedencrypting request command to encrypt the piece according to anencryption algorithm to have an initial result by the SIM; g) packingthe initial result in a response packet and delivering the responsepacket to the mobile phone by the SIM; h) delivering the response packetto the BIP server via the mobile network by the mobile phone; i)repeating the step d) to the step h) for the other request packet; andj) unpacking the response packets to fetch the initial results,combining the encrypted pieces as an encrypted object in a final result,and delivering the final result to the mobile phone for the app by theBIP server, wherein Data delivered between the SIM and the BIP servervia the mobile phone is encrypted.
 12. The method according to claim 11,wherein data between the BIP server and the mobile phone is conformed toHyper Text Transfer Protocol (HTTP).
 13. The method according to claim11, wherein the result unpacked from the response packet is furtherconverted to a format of JSON.
 14. The method according to claim 11,wherein the communication processes between the mobile phone and the BIPserver are further encrypted according to Hyper Text Transfer ProtocolSecure (HTTPS) protocol.
 15. The method according to claim 11, whereinthe request command is verifying an attached Personal IdentificationNumber (PIN) and the SIM compares the PIN with a preset value.
 16. Themethod according to claim 11, wherein the request command is selecting afile and the SIM provides names of all files stored therein as theresult.
 17. The method according to claim 11, wherein the requestcommand is reading a selected file and the SIM provides the selectedfile stored therein as the result.
 18. The method according to claim 11,wherein the encryption algorithm is Advanced Encryption Standard (AES)or Rivest-Shamir-Adleman (RSA).
 19. The method according to claim 11,wherein a type of the SIM is a slim SIM, an eSIM, an integrated SIM(iSIM) or a SIM card.
 20. The method according to claim 11, the step a)further comprises sub-steps of: a1) delivering a token request with aninputted third party number for an app to a BIP server by a mobile phonewhere the app is installed; a2) delivering a temporary permission tokento the app via the mobile phone by the BIP server; a3) delivering abinding request for the app to the BIP server by the mobile phone; anda4) binding the third party number with a registered number in the BIPserver, providing a permanent token to the app and delivering asuccessful binding message to the app via the mobile phone by the BIPserver.
 21. The method according to claim 20, further comprising stepsof: a5) delivering a failed binding message with a binding code to theapp via the mobile phone by the BIP server when the step a4) is failed;a6) delivering the binding code to the BIP server for rebinding by themobile phone; and a7) binding the third party number with a registerednumber in the BIP server again, providing another permanent token to theapp and delivering a successful binding message to the app via themobile phone by the BIP server.
 22. A method for implementing requestsfrom an app by a SIM in a mobile phone, comprising the steps of: a)binding an app to a BIP server by a mobile phone where the app isinstalled; b) delivering a decrypting request command with an encryptedobject to be decrypted to the BIP server by the mobile phone; c) cuttingthe object into a plurality of pieces, converting a plurality of amendeddecrypting request commands in an APDU format from the decryptingrequest command, and packing each amended decrypting request commandwith a specific piece in a request packet, respectively, by the BIPserver; d) delivering one request packet to an IP of a SIM by the BIPserver via a mobile network; e) receiving and unpacking the requestpacket to have the amended decrypting request command and correspondingpiece, and providing the amended decrypting request command with thepiece to the SIM by the mobile phone; f) executing the amendeddecrypting request command to decrypt the piece according to anencryption algorithm to have an initial result by the SIM; g) packingthe initial result in a response packet and delivering the responsepacket to the mobile phone by the SIM; h) delivering the response packetto the BIP server via the mobile network by the mobile phone; i)repeating the step d) to the step h) for the other request packet; andj) unpacking the response packets to fetch the initial results,combining the decrypted pieces as a decrypted object in a final result,and delivering the final result to the mobile phone for the app by theBIP server, wherein Data delivered between the SIM and the BIP servervia the mobile phone is encrypted.
 23. The method according to claim 22,wherein data between the BIP server and the mobile phone is conformed toHyper Text Transfer Protocol (HTTP).
 24. The method according to claim22, wherein the result unpacked from the response packet is furtherconverted to a format of JSON.
 25. The method according to claim 22,wherein the communication processes between the mobile phone and the BIPserver are further encrypted according to Hyper Text Transfer ProtocolSecure (HTTPS) protocol.
 26. The method according to claim 22, whereinthe request command is verifying an attached Personal IdentificationNumber (PIN) and the SIM compares the PIN with a preset value.
 27. Themethod according to claim 22, wherein the request command is selecting afile and the SIM provides names of all files stored therein as theresult.
 28. The method according to claim 22, wherein the requestcommand is reading a selected file and the SIM provides the selectedfile stored therein as the result.
 29. The method according to claim 22,wherein the encryption algorithm is Advanced Encryption Standard (AES)or Rivest-Shamir-Adleman (RSA).
 30. The method according to claim 22,wherein a type of the SIM is a slim SIM, an eSIM, an integrated SIM(iSIM) or a SIM card.
 31. The method according to claim 22, the step a)further comprises sub-steps of: a1) delivering a token request with aninputted third party number for an app to a BIP server by a mobile phonewhere the app is installed; a2) delivering a temporary permission tokento the app via the mobile phone by the BIP server; a3) delivering abinding request for the app to the BIP server by the mobile phone; anda4) binding the third party number with a registered number in the BIPserver, providing a permanent token to the app and delivering asuccessful binding message to the app via the mobile phone by the BIPserver.
 32. The method according to claim 31, further comprising stepsof: a5) delivering a failed binding message with a binding code to theapp via the mobile phone by the BIP server when the step a4) is failed;a6) delivering the binding code to the BIP server for rebinding by themobile phone; and a7) binding the third party number with a registerednumber in the BIP server again, providing another permanent token to theapp and delivering a successful binding message to the app via themobile phone by the BIP server.